✅ All Jest tests passed! This PR is ready to merge.

Summary

Adds an automated workflow to ensure PR titles follow the Conventional Commits standard.

Changes

• Added pr-title-check.yml workflow.
• Enforces format: <type>: <description> or <type>(scope): <description>.
• Supported types: feat, fix, perf, test, docs, ci, etc.
• Provides helpful examples in the logs if a check fails.

Benefits

• Cleaner History: Keeps the main branch readable.
• Enhanced Searchability: Standardized prefixes (fix:, feat:, ci:) make it significantly easier to filter and search the repository's history.
• Industry Standard Compliance: Aligns the project with best practices used by major open-source ecosystems.

great work
commits from the previous pr followed here

✅ All Jest tests passed! This PR is ready to merge.

Summary

Adds an automated workflow to ensure PR titles follow the Conventional Commits standard.

Changes

• Added pr-title-check.yml workflow.
• Enforces format: <type>: <description> or <type>(scope): <description>.
• Supported types: feat, fix, perf, test, docs, ci, etc.
• Provides helpful examples in the logs if a check fails.

Benefits

• Cleaner History: Keeps the main branch readable.
• Enhanced Searchability: Standardized prefixes (fix:, feat:, ci:) make it significantly easier to filter and search the repository's history.
• Industry Standard Compliance: Aligns the project with best practices used by major open-source ecosystems.

great work commits from the previous pr followed here

fixed the commit history

✅ All Jest tests passed! This PR is ready to merge.

@walterbender i ran prettier on the cypress file to resolve the ESLint failures and clear the way for this workflow to be added. not sure why they were flagged, but the checks are passing now.

What exactly does this check other than the title format?

@walterbender it mostly improves searchability and keeps the pr list consistent, making it easier to track changes as the repo grows. let me know if you think this adds enough value or if we should skip it.

@Jetshree i m not in favour of taking this pr ahead for merging PR title is not very big deal cause anything which stays with us is the commit message and i m trying to focus more on the commit message instead of the PR titlte which is temporary. even rewriting the PR title is very easy unlike the commit message which is bit tricky.

@Jetshree i m not in favour of taking this pr ahead for merging PR title is not very big deal cause anything which stays with us is the commit message and i m trying to focus more on the commit message instead of the PR titlte which is temporary. even rewriting the PR title is very easy unlike the commit message which is bit tricky.

That makes sense. I completely respect your perspective on focusing on commit messages instead. Thanks for the feedback.